that bookmark button location on the post actions should be changed
also those lexicons don't look private? unless that's new. It'd be a very bad idea to leave bookmarks publicly exposed.

Valid point, but also Why would it be a bad idea for them to be public? Your likes are also public. More discussion on that here

lexicon-community/lexicon#12

Public everything isn't great and I wish my likes were private but thats more of a protocol issue. Bookmarks being public seems like a poor idea but unfortunately maybe it makes sense but I still think you should change it. Also, move the bookmark button to the far right with only a little big of padding with the menu button.

I agree that it doesn't make sense for bookmarks to be public and there should be no need for that in the lexicon if it can be avoided

Count me in for ‘okay with public bookmarks’. Yeah it’s not ideal, but it’s simply the limitation of the platform as it exists right now, and it’s a great start for client convergence.

The notion of all-public-activity when using Bluesky is already deeply engrained for me, so my use of bookmarks won’t be any different.

Worth noting that the most popular method of bookmarking to date has been to reply with a 📌 to a post. Making that inadvertently noisy practice obsolete would be a big improvement on its own.

Also, here’s a workaround that multi-account clients could easily accommodate:

1. make an anonymous alt-account
2. anything you want to privately bookmark, you bookmark with that account

This shouldn’t have to require constant account switching, as there’s already prior art (in Mastodon at least) for clients that have a UI utility like “repost/favorite from: acc1, acc2..”

I strongly disagree. Likes and blocks are public because they have to be. Bookmarks do not have to be. Parts of Bluesky are "public" because they have to be, it doesn't mean everything is public. Bookmarks being public would allow Cambridge-Analytica like scraping, it would show what a user really liked. It's a very bad idea to make bookmarks public, and the team doesn't seem very interested in that.

@oracularhades my problem with private bookmarks, rather than using an anonymous account, is that it takes away portability. The data for bookmarks would be stored on a private server, which seems wrong at a protocol level, rather than chats being stored on a private server. If anything, it made sense for blocks to be stored privately. Blocking someone can have real-world implications, and its better for those who are blocked to not know.

As for scraping, I don't see a reason why bookmarks are any different than likes or reposts. I could make the argument that reposts are actually what I'm truly interested in and support, and bookmarks are just a way of saving things like recipes to come back to later. That's just the nature of Bluesky, all the data is public.

EDIT:
There is some effort going on internally to support private state on PDS, which, if/when completed, bookmarks would be a great candidate for

my problem with private bookmarks, rather than using an anonymous account, is that it takes away portability. The data for bookmarks would be stored on a private server,

your entire PDS is the portability. That's its job :) - so no, that's not true

It's a very bad idea to make bookmarks public, and the team doesn't seem very interested in that.

@oracularhades is right, bookmarks should be private, like mutes are. Users expect this, as this is how bookmarks work elsewhere (most notably on Twitter). We already have a workaround to make public bookmarks, although it's certainly not ideal. However, it would confuse users to add a built-in bookmark function but with everything you bookmark being public.

It's possible that once we have private bookmarks an option to share some of them publicly would be a good idea (e.g. here's a curated collection of posts on a certain topic), but it's clear from user feedback that private bookmarks must be the first step.

my problem with private bookmarks, rather than using an anonymous account, is that it takes away portability.

@ebwinters Portability can be implemented by allowing users to export their bookmarks into a file and that file can then be imported elsewhere.

As for scraping, I don't see a reason why bookmarks are any different than likes or reposts.

I understand that you personally would be happy for your bookmarks to be public, but it's clear from feedback that there's a strong desire from many users for a way to save posts privately for future reference.

@surfdude29: It's possible that once we have private bookmarks an option to share some of them publicly would be a good idea

I think if we do this it should be "bookmark collections/folders" with an option to make those public, and they can display on the user's profile.

EDIT: @surfdude29 sorry it's 5am and I missed your "(e.g. here's a curated collection of posts on a certain topic)," lmao, you already suggested this.

@surfdude29 I wouldn't be happy with public bookmarks per se, that's just the limits of the protocol right now. I'd rather bookmarks be stored in the PDS for portability, but if private state on the PDS is a thing, that is the ideal solution, and I'd imagine a lexicon/client change would be in store for the community.lexicon.bookmarks schema.

@ebwinters Based on all the feedback I've seen from users on Bluesky, my view is that a fundamental requirement of any implementation of bookmarks in social-app is that they be kept private.

Therefore, I would suggest that we need to wait until this can be done in a way that's consistent with other goals – private state on the PDS seems a promising way to do that – instead of going ahead with public bookmarks as an interim solution, simply because that's all that can be managed at the moment.

I think doing this would be confusing for Bluesky users ("we're releasing a half-finished version of bookmarks, they're all public, but we hope to make them private at some point in the future") and would not meet their expectations.

EDIT: To expand further on my point about user expectations, the overwhelming sense I get from the discussion in #1091 – the main issue relating to bookmarks – is that users expect them to be private. This includes the user who opened the issue, who clarified explicitly in this comment that they want private bookmarks.

What if the (public) bookmarks feature was behind a Labs 🧪 type setting, which also clearly pointed out the public nature of the bookmarks?

Wouldn’t that solve for the divergence in public/private expectations, while also satisfying all the people who want a better alternative than the noisy 📌 hack?